Suggestion of views based on correlation of data

ABSTRACT

The disclosure generally describes methods, software, and systems, including a method for providing a suggested view of asset information for presentation. A set of correlated records is identified for a plurality of assets. The set of correlated records includes a correlated set of at least one characteristic of a particular asset and a characteristic of the non-asset-specific signals. The set of correlated records is analyzed to identify a set of anomaly-detection rules. In a presentation of at least a subset of the assets, an indication of assets associated with a potential anomaly identified. A suggested view is identified based on the potential anomaly and at least one characteristic/signal associated with the determination that the potential anomaly exists. The suggested view is provided for presentation in a user interface.

BACKGROUND

The present disclosure relates to the analysis of large datasets.

Many ways can be used for presenting large amounts of data to users.Data can be categorized into sets, and the information can be presentedusing various presentation methods, including graphs, tables, andcharts. It can be difficult to identify problems or trends in large datasets.

SUMMARY

This disclosure generally describes computer-implemented methods,software, and systems for providing a suggested view of assetinformation for presentation. One computer-implemented method includes:identifying, for a plurality of assets, a set of correlated recordscomprising a correlated set of at least one characteristic of aparticular asset and a characteristic of the non-asset-specific signals;analyzing the set of correlated records to identify a set ofanomaly-detection rules; identifying, in a presentation of at least asubset of the assets, an indication of assets associated with apotential anomaly; identifying a suggested view based on the potentialanomaly and at least one characteristic/signal associated with thedetermination that the potential anomaly exists; and providing thesuggested view for presentation in a user interface.

The foregoing and other implementations can each optionally include oneor more of the following features, alone or in combination. Inparticular, one implementation can include all the following features:

In a first aspect, combinable with any of the previous aspects, theanalyzing the set of correlated records is based on previouslydetermined anomalies and machine learning to identify relevant ordeterminative sets of characteristics.

In a second aspect, combinable with any of the previous aspects,identifying a suggested view based on the potential anomaly and at leastone characteristic/signal associated with the determination that thepotential anomaly exists.

In a third aspect, combinable with any of the previous aspects,identifying the suggested view includes identifying a presentation of aview type.

In a fourth aspect, combinable with any of the previous aspects,identifying the suggested view includes identifying particular sets ofassets and particular characteristics.

In a fifth aspect, combinable with any of the previous aspects, thesuggested view is a product of plural transformations.

In a sixth aspect, combinable with any of the previous aspects, thesuggested view includes color coding of anomalies and different types ofdata.

In a seventh aspect, combinable with any of the previous aspects, thesuggested view provides drill-down and hover capabilities.

In an eighth aspect, combinable with any of the previous aspects, thesuggested view is 1, 2-, 3-, or 4-dimensional.

In a ninth aspect, combinable with any of the previous aspects, thesuggested view includes multiple charts, presented side-by-side.

In a tenth aspect, combinable with any of the previous aspects, thesuggested view includes providing filtering functions by time, region,and type of asset.

In an eleventh aspect, combinable with any of the previous aspects, thesuggested view provides clustering capabilities based on view or zoomlevel.

In a twelfth aspect, combinable with any of the previous aspects, thesuggested view provides stackable layers.

In a thirteenth aspect, combinable with any of the previous aspects, anasset is an Internet of things (IoT) device.

The details of one or more implementations of the subject matter of thisspecification are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages of thesubject matter will become apparent from the description, the drawings,and the claims.

DESCRIPTION OF DRAWINGS

FIG. 1A is a block diagram of an example environment for analyzing largedatasets.

FIG. 1B is a block diagram of an example architecture for providingvisualizations of assets.

FIG. 1C is a screenshot of an example user interface supported by thearchitecture.

FIG. 1D shows an example view.

FIG. 2 is a conceptual diagram showing an example scenario of largeamounts of data received from plural assets over time.

FIG. 3 is a diagram of an example flow of information used for largedataset views.

FIG. 4 is a diagram of an example network of merged information used inviews.

FIG. 5 is a diagram showing example consumption of views by variousentities and applications.

FIG. 6 is a flowchart of an example method for data collection andcorrelation of large numbers of assets.

FIG. 7 is a flowchart of an example method for combining signals withgeospatial and transactional data to generate view referred to in FIG.8.

FIG. 8 is a flowchart of an example method for machine learning anomalydetection.

FIG. 9 is a block diagram of an exemplary computer system used toprovide computational functionalities associated with describedalgorithms, methods, functions, processes, flows, and procedures asdescribed in the instant disclosure.

DETAILED DESCRIPTION

This disclosure generally describes computer-implemented methods,software, and systems for analyzing large datasets. For example, theanalysis can include the use of machine-guided large dataset analyticsand visualization. The techniques described herein can enable datamanagement of raw data (e.g., including millions or more of Internet ofthings (IoT) messages received over time) in order to generatevisualizations (e.g., supporting a user interface that provides visualpresentations and context to the raw data).

In some implementations, the computer-implemented methods, software, andsystems for the analysis of large datasets can include three maincomponents. First, a system can exist that automatically processes andtransforms raw IoT messages and other information that is matched upwith related business and external data to produce views that provide afuller context and/or machine-generated insights (e.g., includinganomalies identified in the data). Second, a self-learning system canimprove the quality of machine-generated insights with human feedbackthat can contextualize the information and improve future insights (thusimproved machine-generated insights). For example, feedback provided bya user can influence anomaly detection predictions provided to otherpeople in the same role, in the same organization, and others. Third, amass data visualizer can provide views for interactive visualization byusers. The mass data visualizer can provide, for example, anout-of-the-box “default” view that is generated generically, includingproviding an overview view into multiple assets and conditions. The massdata visualizer can provide easy navigation to anomalous assets andtheir visualization in multiple perspectives. For example, the systemcan automatically propose and/or place the visualizations into a defaultperspective based on the data and available insights.

The techniques described in this disclosure can provide many advantages.First, the techniques can proactively provide insights on currentconditions in their assets, including providing the ability to manageassets more efficiently. Second, out-of-the-box visualizer can includean interactive tool that provides access to machine-generated insightsthat are readily consumable by non-data scientists. Third, a companythat provides a common out-of-the-box visualizer can maintain a singlecomponent that is re-usable by all customers. Fourth, through the use ofdata views, most user interfaces (UIs) can be realized as visualizationof one or more views, and partners/customer can build their own viewswithout further development by the company. A visualizer can, bydefault, choose dimensions that provide most influence to the anomaly,such as using statistical correlation, which can cause anomalous pointsto cluster in a better way, thus helping the user to identify the causesfor the anomaly and more clearly point out observations.

FIG. 1A is a block diagram of an example environment 100 for analyzinglarge datasets. The illustrated environment 100 includes, or iscommunicably coupled with, at least one server 104 and plural clients106, all connected using a network 102. The environment 100 can be used,for example, to collect and analyze large datasets containinginformation for millions or more of assets 108. The environment 100 canalso be used to provide information about the assets 108, includingvisualizations, on the one or more clients 106. The assets 108 caninclude, for example, IoT devices such as equipment, vehicles, and otherdevices and/or machinery that can be connected or tracked on theInternet or via local networks. For example, the assets 108 can includea company's thousands of vending machines (and/or other stationary IoTdevices) and/or a mobile fleet of trucks that service the IoT devices orare used for other functions. Different assets 108 can be present orused in implementations, including otherwise non-related assets 108which do not have a relation to one or more of the other assets 108.Data for the different assets 108 can be managed within the system or inother, parallel systems (e.g., where each system is specific to aparticular set of related assets 108).

Information and visualizations 109 for the assets 108 that are providedat the one or more clients 106 can be generated using data about theasset 108 that is managed by the server 104 and stored in databases 110,including at least one database management system (DBMS) and/or otherdata structures. Applications 112 at the clients 106 can include, forexample, applications for reviewing asset-related information, includinguser interfaces that provide, to a user 114, visualizations ofasset-related information, including context information regarding largenumbers of the assets 108. Each client 106 comprises an electroniccomputing device operable to provide information to the user 114,including using data (e.g., from databases 110) from the server 104, andpotentially from other sources.

A data collection and correlation engine 116 can obtain asset-specificsignals 118 for the assets 108, such as by using an anomaly detectionengine 142 to enrich views with anomaly states for each record. The datacollection and correlation engine 116 can be provided by, or accessibleto, the server 104. Obtaining the asset-specific signals 118 caninclude, for example, a combination of receiving signals from the assets108 (such as when the assets 108 automatically transmit information,such as hourly, daily, or by some other schedule) and through polling ofthe assets 108 (such as the server 104 periodically or regularly askingfor information from the assets 108). The asset-specific signals 118 canbe stored in a data store of asset characteristics 120. Characteristicsthat define each asset 108 can include, for example, a relativelocation, an absolute location, business data, model number, sensorinformation, and other information about the asset 108. In someimplementations, a particular characteristic may be associated withmultiple assets or a groups of assets, such as information associatedwith a specific subset of vending machines, information about a group oftrucks, or information associated with assets having the same modelnumber, part number, manufacturer, history of use, maintenance schedule,location (e.g., general location), or some other information.Asset-specific signals 118 can include sensor readings, statuses andstates (on/off, functioning/not, opened/closed), a current location, aspeed and direction, a temperature, outside temperature, messages,diagnostic codes, power consumption, and other signals. Asset-specificsignals 118 can be generated by sensors associated with and/or embeddedin particular assets 108. Asset-specific signals 118 for an asset 108can also include business-related data, such as revenue (e.g., collectedby a vending machine). Asset-specific signals 118 can be marked withtimestamps identifying when the signals were received, or timestampsassociated with a piece of collected information (e.g., a temperaturereading at a particular time), or a range of times (e.g., revenuecollected over a 24-hour period).

The data collection and correlation engine 116 can also obtainnon-asset-specific signals 122 from external sources 124. Thenon-asset-specific signals 122, while not tied directly to specificassets 108, can include information for a specific location (e.g.,latitude/longitude or other coordinates) or a region (e.g., city, state,country). The non-asset-specific signals 122 can include, for example,weather information (current or forecast), traffic conditions (e.g.,road construction or an accident), current events (sports, politicalresults, news), social media sentiments (e.g., comments on a productthat can be associated with an asset 108), and other information. Thenon-asset-specific signals 122 can include, for example, informationthat has already been recorded and collected for assets 108, includingrevenue information, historical information, and/or other informationthat is available from external sources 124. For example, externalsources 124 can include related enterprise resource planning (ERP)systems, customer relationship management (CRM) software and/or systems,inventory systems, accounting systems, and other systems. The datacollection and correlation engine 116 can decide which informationreceived from the external sources 124 is to be retained, and theinformation can be stored in a data store of non-asset-specificinformation 126.

The data collection and correlation engine 116 can also correlate someof the received non-asset-specific signals 122 with information for atleast some of the assets 108. The correlation can be based on, forexample, a determined correlation between asset characteristics 120 of aparticular asset 108 and a characteristic of the non-asset-specificsignals 122 that are stored in the data store of non-asset-specificinformation 126. In some implementations, correlation performed by thedata collection and correlation engine 116 can occur in real-time, suchas when asset-specific signals 118 and non-asset-specific signals 122are received, and can use information already stored in the assetcharacteristics 120 and the data store of non-asset-specific information126. In some implementations, historical asset information 128associated with assets 108 can be used in the correlation performed bythe data collection and correlation engine 116. In some implementations,correlation performed by the data collection and correlation engine 116can occur when scheduled or on an as-needed basis. Correlatedinformation can be stored, for example, in a data store of correlatedcharacteristics 130, such as indexed by asset 108, searchable by type orgroup or asset 108, and/or in other ways.

A view suggestion engine 132 can suggest views of information associatedwith the assets 108 and the statistically correlated characteristics130. The view suggestion engine 132 can be provided by, or accessibleto, the server 104 for use on the client 106. The view suggestion engine132 can identify the suggested views 134, for example, by identifying,for a plurality of assets 108, a set of correlated records (from thecorrelated characteristics 130) comprising a correlated set of at leastone characteristic of a particular asset and a characteristic of thenon-asset-specific signals 122. Suggested views 134 can be based, atleast in part, on past views and transformations 136 that have been usedbefore. In some implementations, selection of the specific views andtransformations 136 can depend on identifying the user 114, such asusing user information 138 associated with that user.

The view suggestion engine 132 can analyze the correlatedcharacteristics 130 to identify a set of anomaly-detection rules 140.Analysis can be based on, for example, previously determined anomaliesand machine learning to identify relevant or determinative sets ofcharacteristics. The view suggestion engine 132 can identify, forpresentation of at least a subset of the assets 108, an indication ofassets 108 associated with a potential anomaly.

Once a potential anomaly and associated assets are identified, the viewsuggestion engine 132 can identify one or more suggested views 134 basedon the potential anomaly and at least one characteristic/signalassociated with the potential anomaly. The correlation can be based on,for example, a degree of statistical correlation of thecharacteristic/signal to the anomaly.

Suggested views 134 can be a certain type of presentation or aparticular format, such as a line chart, a bar chart, a column chart, apie chart, a graph, a map, or some combination of formats. Suggestedview can include particular sets of assets and particularcharacteristics, such as to present assets that have conditions orvalues associated with temperature, revenue, power consumption, or othercharacteristics. Any one particular view can be a product of pluraltransformations, each transformation creating a view (or at least anintermediate result) from received asset-specific information,asset-non-specific information, and/or existing views.

The view suggestion engine 132 can provide instructions for presentingthe suggested view in a user interface, such as for presentation to theuser 114. In some implementations, views can include color coding, suchas to accentuate anomalies and different types of data. Views can alsoprovide drill-down and hover capabilities, so that the user 114 can viewspecific non-view information, including information for one or moreassets 108, that is used to produce the view. Views can be one-, two-,three, or multi-dimensional, depending on the type of view and thedimensions represented by the information. Views can allow the user tocollapse information from a higher dimension (e.g., three dimensions)down to a lower dimension (e.g., two dimensions). Views can includemultiple charts or other ways of presenting information, such aspresenting a chart and a table, side-by-side. Views can includefiltering functions, such as to allow the user to include (or exclude)information by time, by region (e.g., selected from a map or list), bytype of asset, or by some other user-selected filter(s). Views can allowfor clustering of information, such as based on a current view and/orzoom level. Views can allow the user to create (and manage presentationof) stackable layers of information. Statistical correlation between ananomaly feature and all other features in relevant views/records can bedetermined and sorted. Statistically correlated features and anomalyfeatures can be chosen and suggested automatically to be included in thesuggested visualization. Statistical correlation (e.g., identified withTrue or False indicators) can be used in color-coding plotted datapoints in the visualization.

An anomaly detection engine 142 can detect anomalies associated with theassets 108. Anomalies can indicate, for example, one or more problemsassociated with one or more of the assets 108, such as temperature,power consumption, revenue, status, or other problems associated with agroup of assets. For example, to detect the anomalies, the anomalydetection engine 142 can use information from the data store of anomalydetection rules 140. The anomaly detection engine 142 can be providedby, or accessible to, the server 104.

The anomaly detection engine 142 can analyze each asset associated witha set of correlated records that define a correlated set of at least onecharacteristic of the particular asset and a characteristic of thenon-asset-specific signals. The analysis can include ananomaly-detection analysis of a plurality of assets using the anomalydetection rules 140. Each anomaly-detection rule can be associated with,for example, a set of conditions determined to be indicative of apotential anomaly. In some implementations, the anomaly detection engine142 can detect an anomaly based solely on the characteristics of aparticular asset 108, such as without the use of non-asset-specificsignals.

Potential anomalies can be identified, for example, from one or morevalues being outside a range or percentile, such as temperature valuesoutside of a recommended or safe temperature range, revenue values belowa normal amount, or some other value(s) that are not expected. Potentialanomalies can be detected, for example, by looking at patterns of valuesover time, such as average or normal values associated with atime-of-day, a day-of-week, or some other time indicator. Potentialanomalies can be detected, for example, based on a comparison withhistoric data from a previous similar period, such as a comparison withlast week's data, or last month's data, or the last time there was asimilar event (e.g., a storm or outage). Anomalies can be calculatedusing training machine learning models that are trained over past dataand that identify fresh records as anomalous or not. Anomalies can alsobe determined using unsupervised techniques, such as that do not requiretraining, e.g., using Kalman filtering. Further, a combination of two ormore value determinations can be used such that the combination of datameets a potential anomaly condition or set of conditions.

The anomaly detection engine 142 can prepare, for presentation to a userin a user interface, an identified anomaly 144 for at least a subset ofthe plurality of assets. Each asset 108 (or groups of assets 108) can beidentified as being in a potential anomalous or non-anomalous statebased on the anomaly-detection analysis. The information that isprepared for presentation to the user can include messages, includingpre-defined messages, along the lines of, “X is happening, and Y iscurrently in effect; is this an anomaly?”

The anomaly detection engine 142 can receive inputs 146 from the userthat identifies at least one asset identified in the presentation asanomalous or as a non-anomalous asset. Based on the received input 146,the anomaly detection engine 142 can modify at least one the particularanomaly-detection rules applied to identify the asset as anomalous, suchas by changing conditions associated with the anomaly-detection rule,including loosening or tightening a threshold based on input provided bythe user. When machine learning models are used for anomaly detection,user feedback (e.g., to identify an anomaly or not) can be added as anadditional feature in the full context view and used to retrain themachine learning model, thus allowing user feedback to influence futureprediction.

In some implementations, the anomaly detection engine 142 can decide tomodify a particular anomaly-detection rule only after, for example, aparticular number (e.g., based on a counter) of inputs have beenreceived, such as from multiple different users. In someimplementations, role-based determinations can be made, such asmodifying a particular anomaly-detection rule only if a user who isconsidered an expert has provided input. An expert indication, forexample, can cause an automatic shift of a rule without a threshold,such as if the user has been determined to be an expert based onproviding quality feedback over time. A number of machine learningmodels can be used to automatically provide higher precedence for inputfrom an expert user, as the expert user's inputs are likely to correlatebetter to the outcome. Once a particular anomaly-detection rule ismodified, the anomaly detection engine 142 can store the rule (orretrain the machine learning model) for future analyses.

At a high level, the server 104 comprises an electronic computing deviceoperable to store and provide access to information for use by theplural clients 106. For example, the server 104 can provide access tothe database 110.

As used in the present disclosure, the term “computer” is intended toencompass any suitable processing device. For example, although FIG. 1Aillustrates a single server 104, the environment 100 can be implementedusing two or more servers 104, as well as computers other than servers,including a server pool. Indeed, the server 104 and the clients 106 maybe any computer or processing device. In some implementations, theserver 104 may be distributed in different locations and coupled usingthe network 102.

The server 104 includes a processor 148 and memory 150. Althoughillustrated as the single processor 148 in FIG. 1A, two or moreprocessors 148 may be used according to particular needs, desires, orparticular implementations of the environment 100. Generally, theprocessor 148 executes instructions and manipulates data to perform theoperations of the server 104. Specifically, the processor 148 executesthe functionality required to receive and process requests from theserver 104. In some implementations, the memory 150 can store thedatabase 110.

The memory 150 may store various objects or data, including caches,classes, frameworks, applications, backup data, business objects, jobs,web pages, web page templates, database tables, repositories storingbusiness and/or dynamic information, and any other appropriateinformation including any parameters, variables, algorithms,instructions, rules, constraints, or references thereto associated withthe purposes of the server 104.

Each client 106 of the environment 100 may be any computing deviceoperable to connect to, or communicate with, other systems via a localdatabase or via the network 102 using a wire-line or wirelessconnection. In general, each client 106 comprises an electronic computerdevice operable to receive, transmit, process, and store any appropriatedata associated with the environment 100 of FIG. 1A.

A request handler 152, e.g., can handle requests received from theclients 106, e.g., for data to be provided from one or more databases110. In some implementations, the database 110 can be implemented usingone or more relational databases and/or other storage structures, andthe stored data may be stored locally or distributed.

The illustrated client 106 further includes a processor 154, a memory156, applications 112 (e.g., a browser), and an interface 158. Theinterface 158 is used by the client 106 for communicating with othersystems in a distributed environment—including within the environment100—connected to the network 102, e.g., other systems communicablycoupled to the network 102 (not illustrated). Generally, the interface158 comprises logic encoded in software and/or hardware in a suitablecombination and operable to communicate with the network 102. Morespecifically, the interface 158 may comprise software supporting one ormore communication protocols associated with communications such thatthe network 102 or interface's hardware is operable to communicatephysical signals within and outside of the illustrated environment 100.

Applications 112, including at least one browser 112 a, can receive andprovide information to the users 114 on each of the respective clients106. As an example, in order to update a web page displayed in a browseron the client 106, the application 112 can provide a request for datafrom one or more databases 110 managed by the server 104.

As illustrated in FIG. 1A, the client 106 includes the processor 154.Although illustrated as the single processor 154 in FIG. 1A, two or moreprocessors 154 may be used according to particular needs, desires, orparticular implementations of the environment 100. Generally, theprocessor 154 executes instructions and manipulates data to perform theoperations of the client 106. Specifically, the processor 154 executesthe functionality required to send requests to the server 104 and toreceive and process responses from the server 104.

The illustrated client 106 also includes a memory 156. The memory 156may store various objects or data, including caches, classes,frameworks, applications, backup data, business objects, jobs, webpages, web page templates, database tables, repositories storingbusiness and/or dynamic information, and any other appropriateinformation including any parameters, variables, algorithms,instructions, rules, constraints, or references thereto associated withthe purposes of the client 106.

The illustrated client 106 comprises a graphical user interface (GUI)160, as shown with respect to and included by the client 106. The GUI160 interfaces with at least a portion of the environment 100 for anysuitable purpose, including user interface screens that displayinformation associated with databases 110, allow queries to submitted,and allow data models to be designed, for example. For example, the userinterface screens can provide user entry fields and/or other user entrycontrols for which a user can provide user inputs, e.g., through theapplications 112. User inputs can include, for example, textual input,selections from controls (e.g., menus, lists, options or otherelements), navigation commands (e.g., cursor/mouse movements), and/orcomplex structures (e.g., files, images, sounds, videos). In someimplementations, user inputs can be associated with a context, e.g., aparticular state or segment of an application.

FIG. 1B is a block diagram of an example architecture 162 for providingvisualizations of assets. For example, the visualizations can bevisualizations of the assets 108. Components of the architecture 162 canprovide users with quick access to a complete data set and can allowusers to correlate data in the complete data set using additional toolssuch as a miniature table 168. A mass data analyzer can providenecessary context for exploration by yielding the connections between,for example, geo-spatial data (provided from a geo-spatial module 170),analytical information (provided by an analytics module 172), andflat-list based data (provided from a mass data table 166). Users canfilter, search, and sort data with simple paradigms (such asdrag-and-drop) while using a set of measures, dimensions, and attributesto allow for flexibility to gather necessary insights. A metric library164, for example, can provide metrics used to correlate the data, andthe metric library 164 can be displayed or hidden.

FIG. 1C is a screenshot of an example user interface 162 a supported bythe architecture 162. Entries 166 a in the miniature table 168 canprovide a visualization of an entire data set in an abstracted manner,such as using lines having different colors that represent differenttypes of values in the data. Lines 174 are shown as differentthicknesses in FIG. 1C to represent different colors. The miniaturetable 168 can also provide individual data points for quick access, suchas by allowing users to click on one data point to quickly scroll to acertain position of the mass data table 166. Both the geo-spatial module170 and the analytics module 172 can be dynamic with regards to theinformation that they present to the user, in a geo-spatial view 170 aand an analytics view 172 b, respectively. Based on the nature of thedata set as well as suggested visualization by the system, both thegeo-spatial module 170 and the analytics module 172 can be replaced withother modules. Such replacement could then change the type ofinformation that is presented to the user, e.g., by replacing one ormore of the spatial view 170 a and the analytics view 172 b withsomething else.

At any point in time, the information that is presented within thearchitecture 162 can be tied to a specific data view that has a set ofattributes, measures, and conditions (e.g., including anomalies).Further, user selections in the mass data table 166 and the miniaturetable 168 can be used to identify and highlight information presentedfor assets 108 provided for display by the geo-spatial module 170 andthe analytics module 172 (in the geo-spatial view 170 a and theanalytics view 172 b, respectively). For example, information that isdisplayed can automatically pan to relevant items, which become visibleand highlighted.

The mass data table 166 can present information, for example, for allassets 108 with selected attributes for a current view (which can beconfigurable). The miniature table 168 can be rendered from one or morecondition attributes, which can determine the color of bars thatrepresent particular entries. For example, the color of a bar can dependon the value of a condition variable. In some implementations, a whitecolor (e.g., based on a zero value for a condition) can be used toindicate that no anomaly exists, and one or more shades of blue (e.g.,based on non-zero values for the condition) can be used to indicate thatan anomaly exists. Other colors and visual distinctions are possible.

The geo-spatial view 170 a provided by the geo-spatial module 170 canshow locations of assets 108 on a map. Data can be aggregated by spatialaggregation 178 to show asset 108 counts at various cluster centers 178,such as how many IoT devices are at a specific location at a currentzoom level of the map. In this way, clustering can be a function of atleast the current zoom level, since as the zoom level increases,clusters may break into smaller clusters.

The analytics view 172 b can provide an analytical view. Controls can beprovided that allows a user to select various dimensions, such astemperature and pressure, in order to generate a graph, plot 176, orother graphical representation showing relationships between thedimensions. Data points can be color-coded according to conditions, suchas higher values being represented using one group of colors (e.g.,primarily reds) and lower values being represented using another groupof colors (e.g., primarily blues). In some implementations, the systemcan either automatically select dimensions and colors, or the system cansuggest dimensions that are likely to most clearly visually separate theconditions, such as based on a correlation between the condition andother view attributes. Two-, three-, and/or four-dimensional graphs canbe displayed.

The number of dimensions that are chosen can allow users to gaindifferent perspectives, for example, on a particular graph to allowusers to make intelligent decisions based on new insights. In someimplementations, a three-dimensional view can be rotated in order tosurface an anomaly that may be hidden from view, such as if another datapoint covers the anomaly's data point in a current perspective. Forexample, rotation controls can be provided by a 3D controller that allowusers to freely rotate graphs and other displayed elements.

A zoom controller can be provided that allows users to drill into acertain section of a graph or gain a bigger picture by zooming out.Hover states can be provided that allow users to identify details of adata point without cluttering the screen in a zoomed-out state. Colordifferentiation can be provided to allow users to overlay, multiply, orseparate values for better insight and/or correlation of data. Stackedlayers can be used, including to display a layer at some distance fromanother layer, or to overlay layers one-to-one.

FIG. 1D shows an example view 180. The view 180 includes a display panel182 in which a search control 183 can be used to select and/or filterelements displayed in the view 180. Status displays 184 can graphicallyand/or numerically indicate statuses, e.g., for assets 108, such asvending machines, that are either On or Off. Asset type displays 185 cangraphically and numerically indicate different types of assets. Alertdisplays 186 can identify numbers of assets that currently have analert, such as correlated to detected anomalies. Controls 187 can beused to select types of presentations, such as scatter plots or graphs,to be displayed in a presentation area 190. Asset information 191, suchas providing power consumption information for assets 108 that havepotential anomalies, can have corresponding graphs 192, such as showingpower consumption over time. The graphs 192 have time periods 194 inwhich one or more anomalies potentially exist. Hovering over a portionof the graphs 192 can cause detailed information 196 to be displayed.Using controls 197, for example, a transformation can occur, such as tocreate another view 198.

FIG. 2 is a conceptual diagram showing an example scenario 200 of largeamounts of data received from plural assets over time. For example, thescenario 200 includes mobile assets 202 and stationary assets 204.Mobile assets 202, for example, can be any types of IoT things in spacethat change location, such as cars, trucks, and other mobile vehicles orequipment. Stationary assets 204 can include equipment that typicallyremains in a fixed position, once installed or delivered, such asvending machines, printers, copiers, security systems, heating/coolingdevices, warehouse equipment, and other equipment and/or machines.

Over time 205, mobile assets 202 can typically transmit information 206such as their location, fuel remaining, status information, equipmentreadings, and other information. Stationary assets 204 can typicallytransmit information 208 such as equipment status, revenue collected,temperature readings, and other information that is provided while eachstationary asset 204 ids in a particular location. Information 206 and208 include time-dependent information, such as information that isprovided at regular intervals, on demand, polled (e.g., from a centralserver), or pushed (e.g., in response to events of interest).Time-dependent information can include readings and/or information thatis a one-time reading (e.g., with timestamp), cumulative information,data applicable to a particular time range, and/or other time-dependentinformation. Time-relatedness of the information 206 and 208, receivedover time 205, is depicted in FIG. 2 as a series of layers 210.

Each of the mobile assets 202 and the stationary assets 204 can havedifferent patterns over time which information 206 and 208 is provided.For example, each type of asset can emit signals directly (e.g., viasensors and transmitters) and/or indirectly (such as through relatedenterprise resource planning (ERP) and customer relationship management(CRM) software and/or systems. A goal of techniques described herein isto capture related information (e.g., including transmitted data pointsand ERP/CRM information) and gain an understanding of and insights intoconditions that exist (e.g., “Why are vending machines in certain areasconsuming more than usual power or providing less than usual revenue?”).

Generally, mobile assets 202, through their movement fromplace-to-place, can produce geo-spatial data, such as a current locationidentified through global positioning system (GPS) capabilities and/orother location tracking systems including radio frequency identifier(RFID), near field communication (NFC), and/or other technologies.

Generally, stationary assets 204 can be assets that reside in aparticular space or location, such as a vending machine placed in aparticular brick-and-mortar location. In some cases, stationary assets204 can be relocated, and in such cases, an assignment to a location canbe temporal. Stationary assets 204 can also serve as location marker,e.g., to provide additional context in space, such as to designate alocation for tools that are stored or otherwise exist in proximity tomachinery (e.g., that is itself a stationary asset 204).

Signals that are produced by the mobile assets 202 and the stationaryassets 204 can include instrument readings (e.g., a series oftemperature readings over time), status information (asset isavailable/on versus unavailable/off), monetary information (e.g.,vending machine revenue for the day), user/customer information (e.g.,who is using the asset, such as a driver in a company car or truck),and/or other information.

In addition to signals that are produced and received, transactions canalso be used in combination with the signals to analyze information. Forexample, transactions can exist for objects that are related to IoTassets, and the transactions can be received by various systems. Exampletransactions can include vending machine logs of “dollar amountstransacted,” a series of alerts associated with a shipment of products,and/or other information extracted from or provided by businesswarehouse (BW) systems.

Space-related and location-related information can also be used incombination with signals received from assets. For example, informationfor a particular geographic area can be used to explain patternsassociated with the use and status of assets. Spaces and/or areas canalso be used to geographically relate and/or provide a container forassets (e.g., IoT devices). A set of spaces can capture and/or bedefined by building plans, city map overlays, geographical informationsystems (GIS), and/or other types of geo-spatial systems, tool, andcontext. Space and area definitions can further be used, for example, asa proxy for injecting external data, such as weather, traffic,emergency, current events, or other information. Space-relatedorganization and designation can change over time.

In order to perform the techniques described herein, metadata can bedefined and/or captured for the mobile assets 202 and the stationaryassets 204. The metadata can be used in models (e.g., upon whichvisualizations are based). The metadata can include, for example, thetype of asset, attributes of the asset, relationships between the assetand information in CRM/ERP and other external systems,space/layout/location information, and time bucket profiles andcalendars. The metadata can include information about views andtransformations, such as definitions of big data views that capture datagenerated by things (e.g., assets) in action, and transformations neededto produce these views and generate new views as needed by users. Insome implementations, incoming IOT messages can be considered as raw“views” in that the IOT messages can be used to construct full contextviews through network transformations and enrichment. Raw messages canalso be treated as implicit views.

FIG. 3 is a diagram of an example flow of information 300 used for largedataset views. For example, the flow of information 300 can begin withthe receipt of geo-spatial information 302 (e.g., location informationfor the mobile assets 202 and the stationary assets 204), IoTtransmissions 304 (e.g., status information, states, and otherinformation received from the mobile assets 202 and the stationaryassets 204), and transaction information 306 (e.g., revenue, cost,and/or other financial information received from CRM/ERP and otherexternal systems). Data that is received can be ingested and can flowinto and through a network of views and transformations 308. All theviews (e.g., views 310 V₁ through V₆) can be consumed by various frontends, such as user interfaces for requesting and viewing views. Data forthe views and transformations 308 that is needed to bring data intothese views can be governed by metadata as described herein.Transformations 312 are represented in the flow of information 300 asarrows connecting the views 310.

FIG. 4 is a diagram of an example network 400 of merged information usedin views. For example, the network 400 can be supplied by ingestedinformation, such as geo-spatial ingestion 402, transaction ingestion404 (including signals received from the mobile assets 202 and thestationary assets 204), and thing/device/asset ingestion 406. Theinformation that is ingested can be merged through a process ofenrichment over time (e.g., a time series). For example, data that isingested can include asset and time dimensions 408 that allow the datato be merged 410. Preconditions can be defined, for example, by whichtime and asset dimensions can be matched immediately upon receipt orsubsequently matched transformations

Various types of time-related and time series data can be collected andused in merging. For example, numeric signals can time instant signals,such as (time, dollar amount) pairs, e.g., [1:00 pm, $30], [1:04 pm,$22], [2:01 pm, $50], and so on. Bucketed time, for example, can include[time range, dollar amount] pairs such as [1-2 pm, $330], [2-3 pm,$202], [3-4 pm, $500], and so on. Time-related signals can also includecategorical information such as [time, category] event pairs, e.g.,[1:00 pm, OVERHEATED], [1:04 pm, DEPARTED], [2:01 pm, DELAYED], and soon. Time-related signals can also include state-related information,such as [time, state] pairs, e.g., [1:00 pm, WAITING], [1:04 pm,IN_TRANSIT], [2:01 pm, ARRIVED], and so on.

Format of time-related information is summarized in Table 1:

TABLE 1 Aligning Axes Instant/ Bucketed/ Instant/ Bucketed/ FROM NumericNumeric Categorical Categorical Instant/ 1:00 pm, $30 NA 1:00-2 pm, N/AN/A Numeric 300 (SUM/AVG) Bucketed/ 1-2 pm, $330 NA aggregation N/A N/ANumeric Instant/ 1:00 pm, 1:00 PM, 1-2 pm, 5 (count N/A 1-2 pm,Categorical OVERHEATED 1(=event of events) TOO_MANY_OVERHEATED_EVENTSoccurred) Bucketed/ 1:00 pm, 1:00 PM, 1-2pm, 30 (time N/A N/ACategorical WAITING 1(=in in waiting state) WAITING state)

Table 1 shows how signals can be converted from one time format (itemsin second column) to destination time format (format named in the columnheader) where possible. For example numeric quantitative data which hastimestamped can be transformed to bucketed format by simpleaggregation—row 2, column 4. The “Bucketed/Numeric” column can indicatebucketing of information. A “Bucketed/Categorical” column can indicate atrend, or even a context related to received time-related information,such as indicating that between 1-2 PM too many overheated events werereceived.

Table 2A shows example attributes that can be assigned to varioustime-related information:

TABLE 2A View Attributes VIEWID NAME TYPE CALENDAR TIME_PROF1 TIMESTAMPTIME_INSTANT TIME_PROF2 HOURLY HOURLY 1 TIME_PROF2 DAILY DAILY 2

Transformations can be used to generate one view from anotherdeclaratively, such as the transformations 312 used to create the views310. Transformations can be based on basis metadata that exists forassets, such as metadata for the mobile assets 202 and the stationaryassets 204. The metadata can include, for example, informationidentifying source views (e.g., an input to one or moretransformations), target views (e.g., the outputs of transformations),types of views (e.g., whether the view is a SQL result, a union, amerge, a relation mapper used for mapping to target relation objects, amaster data add type that is used to add master data attributes to anincoming data item, and custom types), and filters. The structure ofincoming messages is known, for example, as an asset cooler can send amessage consisting of a cooler ID and a temperature. The data elementsin the source message and final target view can be assigned a domain, asshown in examples in Table 2B below. It is possible to start from a dataelement/characteristic/signal in the target view, identify its domain,and then work backwards to find messages which contain data elementswith the same domain. Thus it is possible match target views to inputmessages. Then it is a matter of calculating what transformations areneeded to convert message(s) to the target view.

TABLE 2B Example Domain Default Default Aggregation ID Name DescriptionDatatype Aggregation Domain VM_ID VM_ID Vending INT machine IDTEMPERATURE TEMPERATURE Temperature DEC AVG Temperature DOOR_OPENDOOR_OPEN Door open BOOLEAN COUNT COUNT status EVENT_NAME EVENT_NAMEEvent name STRING COUNT COUNT MATERIAL_ID MATERIAL_ID Material ID INTCOUNT COUNT Count INT REVENUE REVENUE Revenue DEC LATTITUDE LATTITUDELatitude DEC LONGITUDE LONGITUDE Longitude DEC HUMIDITY HUMIDITYHumidity DEC AVG HUMIDITY TIMESTAMP TIMESTAMP Timestamp TIMESTAMP TIMETIME Time INT CITY CITY STRING AREA AREA STRING COUNTRY COUNTRY STRINGCONDITION CONDITION Machine INT classification of data point

Each transformation can have one or more inputs and outputs. In someimplementations, an output of each transformation can be written to adata frame (e.g., a Spark data frame) or some other collection of dataorganized into named columns. This can make each output accessible toany subsequent transformation in a sequence or transformations. Mosttransformations can be expressed using SQL statement, which can maketransformations relatively simple to implement. The same or similartechniques can be used for customer-defined transformations.

Table 3 lists example transformations, with their transformation IDs,their types, and a representative SQL query that can define thetransformation:

TABLE 3 Transformations Table with Associated Types and Queries TRANSIDTRANSTYPE QUERY Tquery1 SQL SELECT col1 as Daily, col12 as Hourly,sum(col13) as Temperature from input* group by col11, col12 Tcode2CUSTOM (some.scala.class.name).execute(sqlContext) -> Produces TempTable named “tcode2” Tquery3 SQL SELECT col11, sum(col13) from tquery3group by col11, col12 Tquery4 SQL SELECT input.col11, tcode2.col11,sum(input.col12) from input left join tcode2 on input.col11 =tcode2.col11 group by input.col1, tcode2.col11 Tcode5 CUSTOM(some.scala.class.name).execute(DStream) STATE -> Produces AnotherDStream

Table 4 describes an example sequence in which transformations are to beexecuted. In some implementations, view and transformation metadata canbe checked to verify that the entire plan for an execution sequence isvalid, for example, to ensure that required inputs for a giventransformation are generated by previous transformations.

TABLE 4 Example Transformation Sequence SEQ Group TRANSID 1 1 Tquery1 21 Tcode2 3 1 Tquery3 4 1 Tquery4 1 2 Tcode5

The first TRANSID can operate, for example, on the raw point streamdata, such as data received directly from the mobile assets 202 and thestationary assets 204. The data structure in this case can be thedevice-specific (e.g., vending machine-specific, or car-specific)message type.

Tables 5 and 6 show example transformation IDs and view IDs for outputand input transformations, respectively. Although separate tables can beused for which is in that case the first transformation in the sequence(e.g., SEQ=1 in Table 4), there need not be separate tables in variousapproaches.

TABLE 5 Output Transformation TRANSID VIEWID tquery1 v1cd tquery1 v1hd

TABLE 6 Input Transformation TRANSID VIEWID tquery1 V1 tquery1 v1hd

In some implementations, functions can be used in transformations. Thefunctions can include, for example, prebuilt functions using complementtransformations. As an example, a function using SPACE(LAT,LONG)->SPACE_ID can map LAT, LONG to a space ID based on spatial masterdata

At transformation runtime, e.g., when one or more output views aregenerated based on a transformation from one or more input views, thetransformation can progress from ingestion to transformations that occurfurther downstream in a sequence. For example, a Spark process can beused that enables the transformation of point-stream/processed data andthe writing of any number of views to a server or other system. Thenumber of views and their composition can be driven by applicationqueries, e.g., that define the transformations.

In some implementations, a sequence of transformations can beorchestrated using a Spark Directed Acyclic Graph (DAG) or similar toolor technique. For example, the Spark DAG can be constructed by readingfrom a Transformations Table (e.g., table 3 or similar table). In thiscase, each TRANSID can be a node on the DAG. Transformations can be oneof various types. When a transformation is of the type SQL, for example,dataframe SQL can accommodate the vast majority of application queryrequirements for the transformation. When a transformation is of thetype CUSTOM, for example, the requirements can be more complex, as somecustom Scala code can be supplied via a class which houses thetransformation logic. For a transformation of type CUSTOMSTATE (e.g.,for streaming transformations only), in order to maintain a statefulDStream during Spark streaming, state update logic can be supplied in acustom class.

Each transformations result can be available to other transformationsvia a temporary Dataframe, e.g., named using the TRANSID. The followingis an example sequence of transformations which form a DAG. During theSpark orchestration that includes output operations, a node on the DAGcan optionally have an output operation associated with it. Theoperation can, for example, store the results of the transformation in aserver or other system. Tables that can be required for the Sparkprocess to construct a write operation are now described for views andtransformations.

A VIEW_CONFIGURATION table (e.g., Table 7) can be used to house viewspecific configurations that are required now or in the future. Forexample, the table can support the concept of writing to main and deltatables, which can require periodic merges, as indicated with a parameterkey of “MERGE INTERVAL SECONDS” in Table 7:

TABLE 7 View Configuration Table VIEWID PARAMETER KEY PARAMETER VALUEv1cd MERGE_INTERVAL_SECS 86400

In some implementations, a DAG setup algorithm can be used for settingup transformations, e.g., with the algorithm being based on thefollowing pseudo-code:

ViewsList <- initialize from metadata Transformations <-Initialize frommetadata inputs <-Initialize from transformations input metadata outputs<-Initialize from transformations output metadata IngestionTopics <-initialize from metadata outputMap <- empty While(notEmpty(transformations)) {   T <- getNext(Transformations)   I <-getInputs(t)   If (I in outputMap)   {     O <- getOutputs(t)    outputMap(O.vewname).Value <- Transform(T, outputMap.getInputs(t))    transformations.remove(T)   } else if (I in IngestionTopics)   {    O <- getOutputs(t)     outputMap(O.vewname).Value <-TransformFromIngestion(T, ProxyViews(kafkatopics.getTopics(I)))    transformations.remove(T)   } }

Additional code can be used to dynamically create a Spark DAG using theSQL, CUSTOM and CUSTOMSTATE transformations.

The following pseudo-code can be used to generate transformations:

Transformations autoGenerateTransformations(outputView) {  ret_Transformations <- empty   penultimateViewSet <- empty  outputMeasures <- getMeasures(outputView)   inputViews <-getInputViews(outputView) // from meta data   inputMeasures <-getMeasures(inputViews) // direct from meta data   // identify inputmeasures needed to produce the output measures   matchingInputMeasures<- matchDomain(inputMeasures,   outputMeasures)      // all outputmeasures must be matched,        // else transformations will beincomplete, not all required data can be produced   viewsCount <- 0  For each inputView in matchingInputMeasures     viewsCount <-viewsCount +1     Measures <- getMeasures(inputView,matchingInputMeasures)     (T, penultimateView) <-  generateViewTransformations( inputView,         outputView, measures,viewsCount*1000)     ret_Transformations <- ret_Transformations +T    penultimateViewSet <- penultimateViewSet+   penultimateView ///Final merge ret_Transformations <- ret_Transformations+mergeTransformation(penultimateViewSet,   outputView) returnTransformations } Transformations generateViewTransformations(inputView, outputView, measures,   transformationSequence) {  ret_transformations <- empty   ret_view <- empty   ifassetType(inputView = assetType(outputView) AND if    TimeProfile(outputVIew) = Timeprofile(inputView)      ret_view<-inputView   else      if TimeProfile(outputVIew) <>Timeprofile(inputView)       tmpView <- changeTimeProfile (inputView,timeProlile(outputView)       t <- createTimeTransformation(inputView,tmpView,         transformationSequence, transformationSequence)      ret_transformations <- ret_transformations +t       (t,tmpview1)<- generateTransformation(tmpView,         outputView,transformationSequence+1)       ret_transformations <-ret_transformations +t       ret_view<- tmpview1     else ifassetType(outputVIew) <> assetType(inputView)       ifRelated(assetType(outputVIew), assetType(inputView))          tmpView <-changeToNextRelation (inputView,           assetType(outputView) //immediate related asset          (t, ret_view )<-createRelationTransformation (inputVIew,           tmpView,transformationSequence       )       ret_transformations <-ret_transformations +t        (t, ret_view)<- generateTransformations(tmpView, outputView,         transformationSequence+1)      ret_transformations <- ret_transformations +t   end if   return(ret_transformations, ret_view) ; }

Once views are created, the views can be merged, e.g., automatically.One of the key goals of merging, for example, is automatically mergingincoming data from various sources containing a variety of data types.For example, using techniques associated with the data architecturedescribed in this document can provide the ability to automaticallymerge time series data of various kinds, such as data related tosensors, transactions, weather, revenue, and other aspects. As a result,it can be possible to automatically merge data to produce a desiredcomposite target view, based on multiple ingestion messages andproviding the capability for unified data exploration.

As an example, the following algorithm can be used for automaticallymerging views. Using the algorithm, a merged view can be generated fromdata that is ingested, e.g., received from mobile and stationary assets.

First, for a given [ingestion viewset, target combined view], a commonaligned viewset is generated. For each [TxSetDef, TempViewsetDef], thetransformation(s) and view(s) needed for merging views are determined.This includes identifying a time profile from the target view and thesource view, and generating transformations view definitions needed toconvert to common intermediate views. TxSetDef is executed to generate aTempViewset. Next, TempViewsets are joined, including selecting neededattributes and measures to generate the target view.

For orchestration, e.g., Spark orchestration, there can be at least twooutput operations types. For example, the outputs can be constantlyinserted into base tables, or the outputs can be handled by writingaggregates, e.g., from Spark.

One of the problems associated with orchestration can be requiring thatall data be processed exactly once, however some techniques, e.g., Sparkstreaming, may only guarantee that a data point is processed at leastonce. This can be due to the use of check-pointing to keep track ofoffsets that are processed, and Spark, for example, may replay all datafrom the last check-pointed offsets after a failure, resulting in somedata being reprocessed. This issue can be solved differently for bothtypes of output operations.

For example, for non-aggregate output operations, a Spark batch “ID”column can be maintained in the target tables. During recovery from acheckpoint, for example, data that is going to be re-processed can bedeleted before the recovery process begins.

The use of aggregate tables can include the use of writing to (e.g.,inserting into) a delta table, which can have performance advantagesover performing table updates and/or maintaining a Spark state.Periodically, delta information can be merged with its main counterpart.However, the use of aggregate tables can have disadvantages including,for example, dealing with late data and dealing with replay of data dueto a checkpoint recovery.

As an example, for an hourly (based on device timestamp) aggregation jobthat is defined, the following records can be inserted into thefollowing delta table by Spark.

TABLE 8 Delta Table COL1 COL2 KPI1 TS (Data) TS (Spark batch) Status abcDef 100 09:00 09:01 N def Ghi 1100 09:45 09:50 N

Shortly after 10, an aggregation job that is executing can look for rowshaving status “N” (e.g., meaning “not merged”). The aggregation job canidentify the time range for these rows and then process all other rowsin this range as a batch. After the aggregation job is executed, thedelta table rows that were processed can be marked with status “M”(e.g., meaning “merged”), as shown in the updated delta table (table 9):

TABLE 9 Updated Delta Table COL1 COL2 KPI1 TS (Data) TS (Spark batch)Status abc Def 100 09:00 09:01 M def Ghi 1100 09:45 09:50 M

At this time, the aggregate table can exist as:

TABLE 10 Aggregate Table COL1 COL2 KPI1 TS (bucket) TS (agg time) abcDef 100 09:00-09:59 10:01 def Ghi 1100 09:00-09:59 10:01

At 10:05, if a late data entry reached the delta table, the aggregatejob can delete the old data in the 09:00-09:59 range in the aggregatetable (Table 12) and reprocess all rows in the delta table (Table 11) inthe range 09:00-09:59:

TABLE 11 Updated Delta Table COL1 COL2 KPI1 TS (Data) TS (Spark batch)Status abc Def 100 09:00 09:01 M def Ghi 1100 09:45 09:50 M aaa aaa 22209:58 10:03 N

TABLE 12 Updated Aggregate Table COL1 COL2 KPI1 TS (bucket) TS (aggtime) abc Def 100 09:00-09:59 10:06 def Ghi 1100 09:00-09:59 10:06 aaaaaa 222 09:00-09:59 10:06

In some implementations, in order to manage the size of the delta table,a reasonable retention period can be specified so that if a late rowarrives, the aggregation job can sees all relevant data in order tofully re-process the time bucket. For example, a reasonable retentionperiod can be such that it's probably okay to delete time buckets in thedelta table that have been aggregated and that are 12-24 hours old, assensor data typically should not arrive after that time. To handlecheckpoint recovery data replay (e.g., breaks of impotency), the“TS(Spark batch)” column can be maintained in the delta table (Table11). During recovery, rows with the same batch TS are to be deleted, andnot re-inserted if the rows already exist. After the data is replayed,the aggregation job can see the new rows and re-aggregate the entiretime buckets.

In some implementations, orchestration can also use metadata caching.For example, the orchestration process would likely need access toseveral metadata objects, either for transformations or to controlorchestration. These metadata objects may be volatile, which can requirethe use of mechanisms to check validity and maintain a consistent viewof the objects. For example, the functionality can be similar to cachesused in digital spaces.

Some implementations of systems that provide visualization can include,for example, “built-in” functionality. The built-in functionality caninclude, for example, application configuration access (e.g., includingtried-and-tested spatial aggregation-related functionality) and ruleengine application programming interfaces (APIs). The built-infunctionality can also include capabilities for data matching use cases,e.g., for connecting to a CRM system in order to map one or more fieldsto an incoming stream data. If an instance (e.g., a Spark applicationinstance) needs access to master data and/or metadata, a CUSTOM objectcan be implemented and supplied via a class. Table 13 (e.g., a cacheobjects table) defines available (and houses a manifest for) cachedobjects and their statuses:

TABLE 13 Cache Objects Table OBJECT OBJECT ID OBJECTNAME SOURCE TYPEobj1 spatialIndex (spatial aggregation use case) BUILTIN transient obj2Some.custom.scala.class CUSTOM static obj3 ingestconfiguration (generalconfiguration) BUILTIN transient obj4 somethingfromCRMsystem (datamatching use case) BUILTIN static obj5 thingtypedefinition (validatedevice messages) BUILTIN static obj6dagconfigurationfromTRANSFORMATIONStable BUILTIN transient

Cached objects identified in Table 13 may have various parameters andconfigurations, such as including a refresh interval. Such parametersand configuration can be included in metadata that is stored in a cachedobject properties table:

TABLE 14 Cache Object Properties Table OBJECTID PARAMKEY PARAMVALUE obj1REFRESH_INTERVAL 3600

Orchestration can also rely on general configuration information such asdefined in the following configuration table that is accessible, forexample, by applications:

TABLE 15 Configuration Table PARAMKEY PARAMVALUE PARAMTYPEstreaminginterval 10 Integer Numpartitions 4 Integer

The categories of views that are available to users can include spatialviews. For example, spatial views can be generated from informationincluded in a raw location stream accessed from storage or received inan actual live stream. Spatial metadata can be used to performspecialized spatial aggregations, such as aggregations that account foror use spatial hierarchies, dynamic aggregations (that occur inreal-time based on data received), and other aggregations.

Aggregations can rely on machine-guided insights. For example, themachine-guided insights can include correlation which, when implementedas a transformation, can provide an output that is a simple view.Parameters for correlation can include, for example, partitions (e.g.,optional list of attributes under which to execute independentcorrelations), inputs (e.g., identifying transformation inputs togenerate a view), and outputs (e.g., including a list of partitionattributes, attribute pair, and correlation values). Outputs can bedefined, for example, in structures such as [partition_attribute,partion_attribute2, attributeA, attribute B, correlation].

Correlation views definitions can be pre-defined in metadata. In thisway, runtime execution can periodically execute transformations torefresh the correlation data.

Another type of transformation is a clustering transformation.Parameters that are used in clustering transformations can include, forexample, one or more lists of attributes to consider for clustering,typically including attributes that are numeric or that can be convertedto numeric during execution. Parameters used in clusteringtransformation can also include output parameters, such as an updatecluster column (e.g., defined in metadata and identifying a clusternumber, a cluster center distance, and a confidence level) and clustercenter information (e.g., generated and/or defined in a separate tableand identifying a cluster center for that view (e.g., of format/content[ClusterID, CenterAttr1, CenterAttr2, . . . , user-defined label(s)]

Runtime execution of clustering transformations can include periodicallyexecuting clustering transformations/models to generate clusterinformation and including, for new data, predicting a cluster bycalculating a distance from cluster centers. Clusters can be correlatedto attributes and measures of the view generated by clustering.

Another type of transformation can result in large datasetvisualizations. This type of visualization can be based on, for example,geo-spatial data, cluster events and states, summary and detail patterns(e.g., cluster visualization (summary) versus cluster representatives(detail)), drag-and-drop capabilities (e.g., used in dragging a clusterand dropping the cluster over a map to see spatial organization ofclusters), automatic rule generation, incorporation of user feedback.User feedback can be received through user interfaces for collectinguser inputs, both implicitly (e.g., based on user inputs) and explicitly(e.g., inferred based on user actions/inputs).

Views and Transformations can include, for example, geo-spatial views inwhich spatial data is generated by movement of things (e.g., the mobileassets 202 and the stationary assets 204). Geo-spatial views canprovides spatial context to signals that are received from assets, suchas IoT devices. Further, geo-spatial views can serve as an intermediaryto other data, such as asset-non-specific, including weather, trafficconditions, and/or other information that be available for particularplace or region. Dimensions for (e.g., information associated with)geo-spatial information include space (e.g., location, includinglatitude, longitude, elevation, names of regions, and/or other locationinformation, an identification of an asset (e.g., a stationary asset),time-related information (e.g., a point in time or a time range), andidentification of mobile assets

Measures that are related to a particular area can include, for example,a number (e.g., indicating a presence) of assets at a location or in aregion, and time spent at the location or in the region.

Transaction views that are based on geo-spatial information can begenerated based on various sources of information, including receivedand ingested transaction data for assets captured through applications.Dimensions/information for each asset can include an identifier of theasset (e.g., the particular IoT thing), and a current time (or timerange). Measures associated with each asset can include, for example,revenue, e.g., a revenue amount attributable to a time range or acumulative revenue amount.

Another type of transformation can result in IoT signal views. Forexample, IOT signal views can be constructed from data generated bydevices and sensors (e.g., signals from assets, or IoT things).Information included in IoT signal views can include an identifier ofthe asset (e.g., identifying the IoT thing), and a time constraint.Measures that are included in IoT signal views can include, for example,temperature, speed, or other measures. Views that can be derived fromIoT signal views consider, for example, that connected goods must beable to leverage all of the data, the ability to easily produce newviews out of existing ones, the ability to join views based on asset(e.g., IoT thing) and time, and the ability to align time axes(including, for example, when time axes are incompatible)

FIG. 5 is a diagram showing example consumption 500 of views 502 byvarious entities and applications. For example, live views 504 can usehistoric data, and the views can be presented as visualizations 506which can include one or more of bar charts 508, line graphs 510, and/orother types of presentations. Anomalies 512 can also be indicated, suchas through different colors or styles of presentation, or by labeling.For example, if the line graph 510 is used to present temperature overtime, the anomaly 512 can be identifies as a “very high” temperaturereading that applies to one or more assets at a specific time or a rangeof times.

All views 514 (e.g., including live views 504 and past views) can beused to support various capabilities and functions, including dataexploration 516 (e.g., correlation and clustering), analytics 518, andgeo-spatial capabilities 520. Views 502 can be used to train (522)dataset models 524, which in turn can help to predict (526) views 502 inwhich a user is likely to be interested. Dataset templates 528 can beused to build (530) the dataset models 524.

In some implementations, a view can be represented as a table of rows,each row representing a data point (e.g., the information for a givenvending machine), and each column representing a variable (e.g., revenuein the last 24 hours). Columns can be added to the table for conditions(e.g., that classify the data) and anomalies (e.g., that indicatewhether or not an anomaly exists, based on the values in the row andoptionally one or more conditions). Conditions can be numeric, Boolean,enumeration, or some other type of value, and groups of rows can eachhave a certain condition.

FIG. 6 is a flowchart of an example method 600 for data collection andcorrelation of large numbers of assets. For clarity of presentation, thedescription that follows generally describes method 600 in the contextof FIGS. 1A-5. For example, after a full context view (e.g., a flatmatrix, as in FIG. 4) is generated, various pieces of information can beput together, including asset-specific signals and characteristics andrelated non-asset signals and characteristics. In addition, an anomalycondition (true or false) can be assigned to each record using asuitable machine learning model. A correlation can be calculated betweenan anomaly feature and at least a subset of other features in the fullcontext view (e.g., using both signals and characteristics). A setfeatures that have the most influence on the anomaly can be identifiedand sorted by correlation. Such features can be chosen to be displayedby default in views, thus providing a most insightful visualpresentation to the user. In some implementations, correlation can becalculated using, for example, Pearson, Spearman, or other standardmethods.

At 602, a set of asset-specific signals is obtained for a plurality ofassets. The data collection and correlation engine 116, for example, canreceive the asset-specific signals 118 associated with the assets 108.The asset-specific signals 118 can include, for each asset 108, arelative location, an absolute location, business data, model number,sensor information, and/or characteristics associated with a group ofassets (including information for a model/part number/manufacture/classof asset). The asset-specific signals 118 can also include, for eachasset 108, sensor readings, statuses (functioning/not, opened/closed),states, monitored data of the asset (e.g., sensor not included as partof the asset), a current location, a temperature, outside temperature(if monitored for that asset), messages, diagnostic codes, and/or powerconsumption. Each signal can have an associated timestamp, including atime when that the signal was received or a time (or time range) forwhich information in the signal represents. Alternatively, a timestampcan be assigned to signals as they are received if no timestamp isassociated with the received signal. Since signals are received overtime, such as in a time series, a series of data points corresponding tovarious points in time or intervals of time can be combined with otherdata points related to assets by matching times or time intervals. Thematching can occur before or after transformations are performed on thedata.

At 604, a set of non-asset-specific signals is obtained. The datacollection and correlation engine 116, for example, can obtain thenon-asset-specific signals 122 from external sources 124. For example,the non-asset-specific signals 122 can be related to a location or place(e.g., a city, state, region, specific building) such as weatherconditions (e.g., current or forecast), current events (e.g., sports,politics, news events, stocks), social media information (e.g., socialmedia posts, trends, product information (e.g., ratings, recalls), andother information. The non-asset-specific signals can be received, forexample, when transmitted from the assets 108, or the non-asset-specificsignals can be polled, for example, by the server 104 requestinginformation from the assets 108.

At 606, at least a portion of the set of non-asset-specific signals iscorrelated with at least some of the plurality of assets based on adetermined correlation between at least one characteristic of aparticular asset and a characteristic of the non-asset-specific signals.For example, the data collection and correlation engine 116 cancorrelate the asset-specific and non-asset-specific information, asdescribed above. The correlation can occur, for example, by matchinglocation information, asset identification information, timestampinformation, and/or other information that can be used to linkasset-specific and non-asset-specific information. Further,asset-specific information can be correlated with other asset-specificinformation, and non-asset-specific information can be correlated withother non-asset-specific information.

At 608, a correlated record of the particular asset comprising thecorrelated characteristics is stored for each asset. As an example, thedata collection and correlation engine 116 can store the correlatedinformation in the data store of correlated characteristics 130.

Characteristics of the asset, such as an IoT device, can include theasset's location. The asset can also be represented in one or morebusiness transactions, such as customer resource management (CRM)systems. As an example, the asset can be a vending machine or a mobilevehicle (e.g., a food truck) that sells one or more specific products,and over time the CRM system can record information about transactionstreams and revenue streams. This information can provide an opportunityfor a time series of revenues to be correlated (e.g., merged) with timeseries sensor signals from assets. In some implementations, the method600 can further include providing information for presenting, in a userinterface, the correlated information. For example, the user interfacecan provide an illustration of at least a subset of the assets in a map,presenting at least a portion of the correlated record at a locationassociated with the asset, such as a stationary location for the vendingmachine or a sales area for the mobile vehicle.

FIG. 7 is a flowchart of an example method 700 for combining signalswith geospatial and transactional data to generate view referred to inFIG. 8. For clarity of presentation, the description that followsgenerally describes method 700 in the context of FIGS. 1A-5.

At 702, a set of correlated records is identified for a plurality ofassets. The set of correlated records comprise a correlated set of atleast one characteristic of a particular asset and a characteristic ofthe non-asset-specific signals. For example, the data collection andcorrelation engine 116 can receive and correlate the asset-specificsignals 118 associated with the assets 108 and the non-asset-specificsignals 122 received from the external sources 124. The correlatedinformation can be stored, for example, in the data store of correlatedcharacteristics 130.

At 704, the set of correlated records is analyzed to identify a set ofanomaly-detection rules. For example, the analysis can be based onpreviously determined anomalies and machine learning to identifyrelevant or determinative sets of characteristics. The anomaly detectionengine 142 can use information in the data store of correlatedcharacteristics 130 to generate the anomaly detection rules 140.Generation of the anomaly detection rules 140 can be based, at least inpart, on past information about anomalies. The past information caninclude, for example, information indicating when a particular set ofcharacteristics indicates a confirmed (e.g., or very likely) anomalyexists and information indicating that a particular set ofcharacteristics indicates that no anomaly exists.

At 706, an indication of assets associated with a potential anomaly isidentified for presentation of at least a subset of the assets. Forexample, the anomaly detection engine 142 can prepare informationidentifying assets 108 for which an anomaly potentially exists alongwith information identified as to why (e.g., based on what specificcurrent or past information the anomaly has been identified.

At 708, a suggested view is identified based on the potential anomalyand at least one characteristic/signal associated with the determinationthat the potential anomaly exists (based on the degree of correlation ofthe characteristic/signal to the anomaly). The view suggestion engine132, for example, can identify a view that encompasses one or moreassets 108 associated with the potential anomaly. The suggested view bea view that presents a line chart, a bar chart, a column chart, a piechart, a graph, a map, or some combination of view types. The suggestedview can include information on particular sets of assets and particularcharacteristics, such as information about temperature, revenue, powerconsumption, or some other data that triggered identification of thepotential anomaly. The suggested view can be a product of pluraltransformations, including one or more transformations that areidentified specifically for presenting information about the potentialanomaly.

At 710, the suggested view is provided for presentation in the UI. Theprepared information can be provided, for example, to the user 114 forpresentation in the GUI 160. The suggested view in include color codingthat helps to accentuate the one or more anomalies as well as tovisually indicate different types of data. The suggested view canprovide drill-down, hover, and other data discovery capabilities. Thesuggested view can be 1-, 2-, 3-, or 4-dimensional and can includemultiple charts and information presentation areas, side-by-side. Thesuggested view can include filtering functions, such as to limitpresentation of information by time, by region, by type of asset, or bycombinations of filtering functions. The suggested view can provideclustering of information, such as based on a current view or zoomlevel. The suggested view can provide stackable layers of information,such as to allow the user 114 to remove information no longer ofinterest or to present additional information.

FIG. 8 is a flowchart of an example method 800 for machine learninganomaly detection. For clarity of presentation, the description thatfollows generally describes method 800 in the context of FIGS. 1A-5.

At 802, based on an anomaly-detection analysis of a plurality of assetsusing a set of anomaly-detection rules, each asset is analyzed that isassociated with a set of correlated records comprising a correlated setof at least one characteristic of the particular asset and acharacteristic of the non-asset-specific signals. Each anomaly-detectionrule is associated with a set of conditions determined to be indicativeof a potential anomaly. Potential anomalies can be identified, forexample, from one or more values being outside a range or percentile.Identification can occur, for example, by looking at patterns,information associated with time-of-day or a day-of-week, or some othertime-based comparison. Identification can occur, for example, bycomparing a particular value with historic data from a previous similarperiod, such as last week's data, or last month's data, or the last timethere was a storm. In some implementations, a given anomaly-detectionrule can be associated with a set of conditions determined to beindicative of a potential anomaly. In some implementations, analysis ofthe asset can include the use of a suitable unsupervised machinelearning model that detects anomalies. In some implementations, set ofanomaly-detection algorithms can be applied on a given generated view(e.g., view 502 described above with reference to FIG. 5) to provide anadditional feature. For example, the additional feature can be capturedin and represented by a column in a table that represents the view, suchas a column named “Anomaly” that holds the value of True (for anomalousdata) or False (for normal data).

At 804, information for at least a subset of the plurality of assets isprovided for presentation in a user interface. Each asset can beidentified as being a potential anomalous or non-anomalous state basedon the anomaly-detection analysis. For example, the potential anomalousor non-anomalous state can be associated with information presented tothe user along the lines of, “X is happening and Y is in effect; is thisan anomaly?”

At 806, input is received from a user identifying at least one assetidentified in the presentation as anomalous as a non-anomalous asset.For example, the anomaly detection engine 142 can receive the userresponses 146 indicating that the potential anomaly is not an anomaly atall, such as if the user 114 knows a valid reason for a value beingout-of-range.

At 808, based on the received input, at least one of the particularanomaly-detection rules applied to identify the asset as anomalous ismodified. For example, based on the user's response 146, the anomalydetection engine 142 can update the anomaly detection rules 140.Specifically, modifying the rule can be done by changing conditionsassociated with the anomaly detection rule, such as by loosening ortightening a test condition or a threshold for the rule.

At 810, the modified rule is stored for future analyses. For example,the anomaly detection engine 142 can store the updated rule in theanomaly detection rules 140.

FIG. 9 is a block diagram of an exemplary computer system 900 used toprovide computational functionalities associated with describedalgorithms, methods, functions, processes, flows, and procedures asdescribed in the instant disclosure.

The illustrated computer 902 is intended to encompass any computingdevice such as a server, desktop computer, laptop/notebook computer,wireless data port, smart phone, personal data assistant (PDA), tabletcomputing device, one or more processors within these devices, or anyother suitable processing device, including both physical or virtualinstances (or both) of the computing device. Additionally, the computer902 may comprise a computer that includes an input device, such as akeypad, keyboard, touch screen, or other device that can accept userinformation, and an output device that conveys information associatedwith the operation of the computer 902, including digital data, visual,or audio information (or a combination of information), or a GUI.

The computer 902 can serve in a role as a client, network component, aserver, a database or other persistency, or any other component (or acombination of roles) of a computer system for performing the subjectmatter described in the instant disclosure. The illustrated computer 902is communicably coupled with a network 930. In some implementations, oneor more components of the computer 902 may be configured to operatewithin environments, including cloud-computing-based, local, global, orother environment (or a combination of environments).

At a high level, the computer 902 is an electronic computing deviceoperable to receive, transmit, process, store, or manage data andinformation associated with the described subject matter. According tosome implementations, the computer 902 may also include or becommunicably coupled with an application server, e-mail server, webserver, caching server, streaming data server, business intelligence(BI) server, or other server (or a combination of servers).

The computer 902 can receive requests over network 930 from a clientapplication (for example, executing on another computer 902) andresponding to the received requests by processing the said requests inan appropriate software application. In addition, requests may also besent to the computer 902 from internal users (for example, from acommand console or by other appropriate access method), external orthird-parties, other automated applications, as well as any otherappropriate entities, individuals, systems, or computers.

Each of the components of the computer 902 can communicate using asystem bus 903. In some implementations, any or all of the components ofthe computer 902, both hardware or software (or a combination ofhardware and software), may interface with each other or the interface904 (or a combination of both) over the system bus 903 using anapplication programming interface (API) 912 or a service layer 913 (or acombination of the API 912 and service layer 913). The API 912 mayinclude specifications for routines, data structures, and objectclasses. The API 912 may be either computer-language independent ordependent and refer to a complete interface, a single function, or evena set of APIs. The service layer 913 provides software services to thecomputer 902 or other components (whether or not illustrated) that arecommunicably coupled to the computer 902. The functionality of thecomputer 902 may be accessible for all service consumers using thisservice layer. Software services, such as those provided by the servicelayer 913, provide reusable, defined business functionalities through adefined interface. For example, the interface may be software written inJAVA, C++, or other suitable language providing data in extensiblemarkup language (XML) format or other suitable format. While illustratedas an integrated component of the computer 902, alternativeimplementations may illustrate the API 912 or the service layer 913 asstand-alone components in relation to other components of the computer902 or other components (whether or not illustrated) that arecommunicably coupled to the computer 902. Moreover, any or all parts ofthe API 912 or the service layer 913 may be implemented as child orsub-modules of another software module, enterprise application, orhardware module without departing from the scope of the instantdisclosure.

The computer 902 includes an interface 904. Although illustrated as asingle interface 904 in FIG. 9, two or more interfaces 904 may be usedaccording to particular needs, desires, or particular implementations ofthe computer 902. The interface 904 is used by the computer 902 forcommunicating with other systems in a distributed environment that areconnected to the network 930 (whether illustrated or not). Generally,the interface 904 comprises logic encoded in software or hardware (or acombination of software and hardware) and operable to communicate withthe network 930. More specifically, the interface 904 may comprisesoftware supporting one or more communication protocols associated withcommunications such that the network 930 or interface's hardware isoperable to communicate physical signals within and outside of theillustrated computer 902.

The computer 902 includes a processor 905. Although illustrated as asingle processor 905 in FIG. 9, two or more processors may be usedaccording to particular needs, desires, or particular implementations ofthe computer 902. Generally, the processor 905 executes instructions andmanipulates data to perform the operations of the computer 902 and anyalgorithms, methods, functions, processes, flows, and procedures asdescribed in the instant disclosure.

The computer 902 also includes a memory 906 that holds data for thecomputer 902 or other components (or a combination of both) that can beconnected to the network 930 (whether illustrated or not). For example,memory 906 can be a database storing data consistent with thisdisclosure. Although illustrated as a single memory 906 in FIG. 9, twoor more memories may be used according to particular needs, desires, orparticular implementations of the computer 902 and the describedfunctionality. While memory 906 is illustrated as an integral componentof the computer 902, in alternative implementations, memory 906 can beexternal to the computer 902.

The application 907 is an algorithmic software engine providingfunctionality according to particular needs, desires, or particularimplementations of the computer 902, particularly with respect tofunctionality described in this disclosure. For example, application 907can serve as one or more components, modules, applications, etc.Further, although illustrated as a single application 907, theapplication 907 may be implemented as multiple applications 907 on thecomputer 902. In addition, although illustrated as integral to thecomputer 902, in alternative implementations, the application 907 can beexternal to the computer 902.

There may be any number of computers 902 associated with, or externalto, a computer system containing computer 902, each computer 902communicating over network 930. Further, the term “client,” “user,” andother appropriate terminology may be used interchangeably as appropriatewithout departing from the scope of this disclosure. Moreover, thisdisclosure contemplates that many users may use one computer 902, orthat one user may use multiple computers 602.

In some implementations, components of the environments and systemsdescribed above may be any computer or processing device such as, forexample, a blade server, general-purpose personal computer (PC),Macintosh, workstation, UNIX-based workstation, or any other suitabledevice. In other words, the present disclosure contemplates computersother than general purpose computers, as well as computers withoutconventional operating systems. Further, components may be adapted toexecute any operating system, including Linux, UNIX, Windows, Mac OS®,Java™, Android™, iOS or any other suitable operating system. Accordingto some implementations, components may also include, or be communicablycoupled with, an e-mail server, a web server, a caching server, astreaming data server, and/or other suitable server(s).

Processors used in the environments and systems described above may be acentral processing unit (CPU), an application specific integratedcircuit (ASIC), a field-programmable gate array (FPGA), or anothersuitable component. Generally, each processor can execute instructionsand manipulates data to perform the operations of various components.Specifically, each processor can execute the functionality required tosend requests and/or data to components of the environment and toreceive data from the components of the environment, such as incommunication between the external, intermediary and target devices.

Components, environments and systems described above may include amemory or multiple memories. Memory may include any type of memory ordatabase module and may take the form of volatile and/or non-volatilememory including, without limitation, magnetic media, optical media,random access memory (RAM), read-only memory (ROM), removable media, orany other suitable local or remote memory component. The memory maystore various objects or data, including caches, classes, frameworks,applications, backup data, business objects, jobs, web pages, web pagetemplates, database tables, repositories storing business and/or dynamicinformation, and any other appropriate information including anyparameters, variables, algorithms, instructions, rules, constraints, forreferences thereto associated with the purposes of the target,intermediary and external devices. Other components within the memoryare possible.

Regardless of the particular implementation, “software” may includecomputer-readable instructions, firmware, wired and/or programmedhardware, or any combination thereof on a tangible medium (transitory ornon-transitory, as appropriate) operable when executed to perform atleast the processes and operations described herein. Indeed, eachsoftware component may be fully or partially written or described in anyappropriate computer language including C, C++, Java™, Visual Basic,assembler, Perl®, any suitable version of 4GL, as well as others.Software may instead include a number of sub-modules, third-partyservices, components, libraries, and such, as appropriate. Conversely,the features and functionality of various components can be combinedinto single components as appropriate.

Devices can encompass any computing device such as a smart phone, tabletcomputing device, PDA, desktop computer, laptop/notebook computer,wireless data port, one or more processors within these devices, or anyother suitable processing device. For example, a device may comprise acomputer that includes an input device, such as a keypad, touch screen,or other device that can accept user information, and an output devicethat conveys information associated with components of the environmentsand systems described above, including digital data, visual information,or a graphical user interface (GUI). The GUI interfaces with at least aportion of the environments and systems described above for any suitablepurpose, including generating a visual representation of a web browser.

The preceding figures and accompanying description illustrate exampleprocesses and computer implementable techniques. The environments andsystems described above (or their software or other components) maycontemplate using, implementing, or executing any suitable technique forperforming these and other tasks. It will be understood that theseprocesses are for illustration purposes only and that the described orsimilar techniques may be performed at any appropriate time, includingconcurrently, individually, in parallel, and/or in combination. Inaddition, many of the operations in these processes may take placesimultaneously, concurrently, in parallel, and/or in different ordersthan as shown. Moreover, processes may have additional operations, feweroperations, and/or different operations, so long as the methods remainappropriate.

In other words, although this disclosure has been described in terms ofcertain implementations and generally associated methods, alterationsand permutations of these implementations, and methods will be apparentto those skilled in the art. Accordingly, the above description ofexample implementations does not define or constrain this disclosure.Other changes, substitutions, and alterations are also possible withoutdeparting from the spirit and scope of this disclosure.

What is claimed is:
 1. A computer-implemented method comprising:identifying, for a plurality of assets, a set of correlated recordscomprising a correlated set of at least one characteristic of aparticular asset and a characteristic of the non-asset-specific signals;analyzing the set of correlated records to identify a set ofanomaly-detection rules; identifying, in a presentation of at least asubset of the assets, an indication of assets associated with apotential anomaly; identifying a suggested view based on the potentialanomaly and at least one characteristic/signal associated with thedetermination that the potential anomaly exists; and providing thesuggested view for presentation in a user interface.
 2. Thecomputer-implemented method of claim 1, wherein the analyzing the set ofcorrelated records is based on previously determined anomalies andmachine learning to identify relevant or determinative sets ofcharacteristics.
 3. The computer-implemented method of claim 1, whereinidentifying a suggested view based on the potential anomaly and at leastone characteristic/signal associated with the determination that thepotential anomaly exists.
 4. The computer-implemented method of claim 1,wherein identifying the suggested view includes identifying apresentation of a view type.
 5. The computer-implemented method of claim1, wherein identifying the suggested view includes identifyingparticular sets of assets and particular characteristics.
 6. Thecomputer-implemented method of claim 1, wherein the suggested view is aproduct of plural transformations.
 7. The computer-implemented method ofclaim 1, wherein the suggested view includes color coding of anomaliesand different types of data.
 8. The computer-implemented method of claim1, wherein the suggested view provides drill-down and hovercapabilities.
 9. The computer-implemented method of claim 1, wherein thesuggested view is 1, 2-, 3-, or 4-dimensional.
 10. Thecomputer-implemented method of claim 1, wherein the suggested viewincludes multiple charts, presented side-by-side.
 11. Thecomputer-implemented method of claim 1, wherein the suggested viewincludes providing filtering functions by time, region, and type ofasset.
 12. The computer-implemented method of claim 1, wherein thesuggested view provides clustering capabilities based on view or zoomlevel.
 13. The computer-implemented method of claim 1, wherein thesuggested view provides stackable layers.
 14. The computer-implementedmethod of claim 1, wherein an asset is an Internet of things (IoT)device.
 15. A system comprising: memory storing information aboutassets; and a server performing operations comprising: identifying, fora plurality of assets, a set of correlated records comprising acorrelated set of at least one characteristic of a particular asset anda characteristic of the non-asset-specific signals; analyzing the set ofcorrelated records to identify a set of anomaly-detection rules;identifying, in a presentation of at least a subset of the assets, anindication of assets associated with a potential anomaly; identifying asuggested view based on the potential anomaly and at least onecharacteristic/signal associated with the determination that thepotential anomaly exists; and providing the suggested view forpresentation in a user interface.
 16. The system of claim 15, whereinthe analyzing the set of correlated records is based on previouslydetermined anomalies and machine learning to identify relevant ordeterminative sets of characteristics.
 17. The system of claim 15,wherein identifying a suggested view based on the potential anomaly andat least one characteristic/signal associated with the determinationthat the potential anomaly exists.
 18. A non-transitorycomputer-readable media encoded with a computer program, the computerprogram comprising instructions that when executed by one or morecomputers cause the one or more computers to perform operationscomprising: identifying, for a plurality of assets, a set of correlatedrecords comprising a correlated set of at least one characteristic of aparticular asset and a characteristic of the non-asset-specific signals;analyzing the set of correlated records to identify a set ofanomaly-detection rules; identifying, in a presentation of at least asubset of the assets, an indication of assets associated with apotential anomaly; identifying a suggested view based on the potentialanomaly and at least one characteristic/signal associated with thedetermination that the potential anomaly exists; and providing thesuggested view for presentation in a user interface.
 19. Thenon-transitory computer-readable media of claim 18, wherein theanalyzing the set of correlated records is based on previouslydetermined anomalies and machine learning to identify relevant ordeterminative sets of characteristics.
 20. The non-transitorycomputer-readable media of claim 18, wherein identifying a suggestedview based on the potential anomaly and at least onecharacteristic/signal associated with the determination that thepotential anomaly exists.